|
|
The matrix below shows you the changes made to each service release of Websydian and what platforms are affected. You will also be able to identify changes that affect the development environment of Websydian indicating if you are required to generate and build your existing functions in order to take advantage of the fix.
When upgrading to Websydian v6.5 you are required to obtain new site keys for the Websydian patterns and a new license file for your Websydian Server.
| Release | Description | Issue # | Java | IBM i | Windows | Gen/Build | Notes |
|---|---|---|---|---|---|---|---|
| v6.5 | Allow request parameters in both the query string and the http-body for POST requests. | 40304 | x | x | x | ||
| UUID system entity for replacing the surrogate system with a true UUID. | x | x | x | Guide | |||
| Enhancement: PageGenerator now support input by memory. | x | x | x | x | |||
| Check box fields now output the correct value for not selected state. Fixes an issue with signature error if adding a check box field to the hidden variable of the event handler | 43475 | x | x | x | x | ||
| Fix: Solved issue with J2EEProxy not picking up the default HTTP body encoding setting in the obuser.properties configuration file. | 42872 | x | |||||
| Enhancement: Support UTF-8 encoded requests and convert to local encoding. Windows only. | x | x | |||||
| Fix: Function ExtractContentType now removes double and single quotes from the character set specified on the request. | x | x | x | x | |||
| StringFunctions.RemoveSingleQuotes renamed to RemoveQuotes and extended to remove both singlequotes and doublequotes from the beginning and end of the string. | x | x | x | x | |||
| "End" button added to the CreateWSDL function | x | x | x | Guide | |||
| CreateWSDL - code too large reported when building CreateWSDL function | 39623 | x | |||||
| Handling requests with transfer-encoding: "chunked" content in SoapProcessors | 40032 | x | x | x | |||
| In the WinC variant, the function DomServices.LoadDocumentFromString did not write error messages to the error stack when the document was invalid. | 42207 | x | |||||
| Parameter mapping when creating simple header elements in the
SoapGenerator.
When you have specified fields in the SimpleHeader input variable for the SoapGenerator, these fields should automatically have been mapped to the Header.InsertRow call. This mapping was not in place. This resulted in missing values for SOAP headers. The mapping has been added and the header values will be mapped automatically. |
41311 | x | x | x | |||
| New option ProhibitDTD for the MSXML parser. | 42209 | ||||||
| Change to PageGeneratorWithFieldConversion. When a field that
has the controltype checkbox occurred in the Hidden variable of an
EventHandler, a signature error would occur if the PageGenerator
had written a blank value to the page. This is due to the special
handling of check box fields in the EventHandler, where a blank
value in the request string is converted to the "false" value of
the field.
The PageGenerator has been changed so that a blank value of a checkbox field in WsyDetails or WsyGrid will be exchanged with the "false" value of the field. This behavior is implemented as the default behavior of the PageGeneratorWithFieldConversion, but it can be removed by setting the function option SetCheckBoxFalseForBlank to No for the PageGenerator. |
43475 | x | x | x | x | ||
| New option for grid pages: WSYD Control Grid Load. If you set
this function option for a function inheriting from
WSYUTIL/GridPage a new control field LoadGrid in the loacl variable
Gridloop is set to No if all the fields in the Position variable is
empty. When this field is set to No, the content of the grid will
not be loaded.
In this way, you can avoid loading the grid until search criteria has been specified. You can also use the field LoadGrid in the GridLoop variable to create your own logic for controlling the load of grid data - just set the value to *No to avoid loading the grid. |
43035 | x | x | x | x | ||
| v6.1.4 | TransacXML adds support for performing XML document validation against Schemas | x | x | Documentation | |||
| Websydian runtime upgraded to support MS XML 6.0 | x | Guide | |||||
| Removed redundant IdentifyInputFields from EventHandler objects of the WSYSHOP pattern | x | x | x | ||||
| Changes to the _DocumentTemplateGenerator removing unwanted scoped ghost objects | x | x | x | Guide | |||
| Websydian Java Servlet runtime improved for handling firewall idle timeout cut off | x | Guide | |||||
| Fix to the script marker %LEN in order for it to work correctly | x | x | x | x | |||
| Fixed problem with XMLHandler in case of blank SoapAction source code | x | x | x | x | Guide | ||
| New option "Full grid load" for GridPage functions enabling output of all records in table to grid | x | x | x | Documentation | |||
| v6.1.2 |
Major licensing improvements to the Websydian Server.
|
x | x | x | |||
| v6.1.1 | Major performance improvements to TransacXML Java based web
service applications. Read the document "Performance considerations for TransacXML" |
x | x | Guide | |||
| Support for deploying TransacXML Java based web service
applications on IBM i Java virtual machine 32 bit version. |
x | Guide | |||||
| Support for Apache distributions of Xerces and Xalan instead of
the Sun distribution. Note! Make sure that you include the supplied xerces and xalan jar files during deployment. |
x | Guide | |||||
| Fix to ensure that temporary filenames are all unique | x | ||||||
| v6.1 | General available major version, read the what is new and upgrade guides. | x | x | x | x | Guide |
Make sure that you read the different guides and documents on changes made to the releases that have been released prior to the one you are currently using.
Then go to our download site and download Websydian v6.5 from our download site at http://www.websydian.com
Follow the normal procedure for installing Websydian patterns making sure that you extract from the new patterns and set the version and level for each Websydian patterns correctly as described in the manual.
Then make sure that you update your runtime environment with the latest dll and jar files as supplied with Websydian v6.5.
In order to take advantage of any changes that requires generate and build you will need to do so, otherwise you can leave your other runtime object alone until you are ready to adopt these changes.
For the Websydian Web Server component make sure that you deploy a new WAR file using the packaging tool.
Online
documentation - Websydian v6.5